-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(x/staking): allow zero unbonding time #19779
Conversation
WalkthroughWalkthroughThe changes aim to enhance the flexibility of the staking module by expanding the validation criteria for the unbonding time. Previously required to be strictly positive, the unbonding time can now be zero or positive, providing more options for setting unbonding times. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: .coderabbit.yml
Files selected for processing (1)
- x/staking/types/params.go (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- x/staking/types/params.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks this makes sense
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: .coderabbit.yml
Files selected for processing (1)
- x/staking/CHANGELOG.md (1 hunks)
Additional comments: 1
x/staking/CHANGELOG.md (1)
- 34-34: The changelog entry for allowing
unbonding_time
to be set to zero is clear and concise, directly linking to the PR for more details.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: .coderabbit.yml
Files selected for processing (1)
- x/staking/keeper/msg_server_test.go (1 hunks)
Additional comments: 1
x/staking/keeper/msg_server_test.go (1)
- 1173-1173: The error message assertion in
TestMsgUpdateParams
has been updated from "unbonding time must be positive" to "unbonding time must not be negative." This change aligns with the PR's objective to allow the unbonding time parameter to be set to zero, indicating that the validation logic now accepts zero or positive values for unbonding time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: .coderabbit.yml
Files selected for processing (2)
- x/staking/CHANGELOG.md (1 hunks)
- x/staking/keeper/msg_server_test.go (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- x/staking/keeper/msg_server_test.go
Additional comments: 1
x/staking/CHANGELOG.md (1)
- 34-34: The entry for allowing
unbonding_time
to be set to zero is correctly placed under the "Improvements" section and follows the changelog's format. However, it's essential to ensure that the documentation elsewhere in the project is updated to reflect this change, especially in user-facing materials where the implications of settingunbonding_time
to zero are explained.
Description
Allows for zero unbonding time
Closes: #XXXX
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
in the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
Summary by CodeRabbit
unbonding_time
to zero, providing more flexibility to users.